ci: use new cache actions (only) - #610
Merged
Merged
Conversation
AlexanderLanin
requested review from
FScholPer,
MaciejKaszynski,
NicolasFussberger,
anmittag,
antonkri,
pawelrutkaq and
ramceb
as code owners
September 7, 2026 14:22
MaciejKaszynski
requested a deployment
to
workflow-approval
September 9, 2026 06:56 — with 
GitHub Actions
Waiting
GitHub Actions
Waiting
MaciejKaszynski
requested a deployment
to
workflow-approval
September 9, 2026 06:56 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
MaciejKaszynski
approved these changes
Sep 9, 2026
github-project-automation
Bot
moved this from Backlog
to Done
in LCM - Lifecycle & Health FT
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use new setup-bazel-cache action. The main goal is to validate the improved cache handling actions.
Contrary to #607 and #608, this will upgrade only the well established action for now, and not the central workflows.
Stage: early adopter. Some of our internal repos already use it, and report mixed/positive results. We need to roll it out on a public repository, to facilitate better analysis options.